x86/mm: Avoid spurious deadlock panic trigger
authorAndres Lagar-Cavilla <andres@lagarcavilla.org>
Thu, 26 Jan 2012 13:21:27 +0000 (13:21 +0000)
committerAndres Lagar-Cavilla <andres@lagarcavilla.org>
Thu, 26 Jan 2012 13:21:27 +0000 (13:21 +0000)
commit3a71f3f3392a92c9a78a0b429c50c66fc589e307
tree0ceeea186bec380570f6a9142073a70cbddc8938
parentbe1ff5e8f0f71f0927ec2681ec7f51ac2efe50d9
x86/mm: Avoid spurious deadlock panic trigger

In the mm layer, if we take lock A, then lock B, and the recursively lock A,
the deadlock detector panics. This is not a deadlock risk because we
already 'own' the outer lock (A), so we will not contend for that resource.

Signed-off-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Acked-by: Tim Deegan <tim@xen.org>
Committed-by: Tim Deegan <tim@xen.org>
xen/arch/x86/mm/mm-locks.h